bitkeeper revision 1.1389.15.10 (428202c9Vz9xfNsG-q-WtZpPrER7xQ)
authorcl349@firebug.cl.cam.ac.uk[cl349] <cl349@firebug.cl.cam.ac.uk[cl349]>
Wed, 11 May 2005 13:04:09 +0000 (13:04 +0000)
committercl349@firebug.cl.cam.ac.uk[cl349] <cl349@firebug.cl.cam.ac.uk[cl349]>
Wed, 11 May 2005 13:04:09 +0000 (13:04 +0000)
commitb7c498208cf4d26f4c34962035873cbe0dac525a
treea8a51b4b583c5527a196075cdb7ba01f2fdfb04a
parente7e68bca44b95d9efe6b847e1d7755fec1b112a8
bitkeeper revision 1.1389.15.10 (428202c9Vz9xfNsG-q-WtZpPrER7xQ)

[PATCH] xen,tools: pincpu use vcpu and cpumap_t

The following patch updates the dom0 pincpu operation to read the VCPU
value from the xend interface rather than hard-coding the exec_domain to
0.  This prevented pinning VCPUS other than 0 to a particular cpu.  The
pincpu cpu argument is replaced with cpumap, a u64 bitmap representing
which CPUs a VCPU can use.

I added the number of VCPUS to the main xm list output and also included
a new sub-option to xm list to display the VCPU to CPU mapping.  While
working on the pincpu code, I fixed an out-of-bounds indexing for the
pincpu operation that wasn't previously exposed since the
vcpu/exec_domain value was hard-coded to 0.

Signed-off-by: Ryan Harper <ryanh@us.ibm.com>
Signed-off-by: Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
15 files changed:
tools/libxc/xc.h
tools/libxc/xc_domain.c
tools/python/xen/lowlevel/xc/xc.c
tools/python/xen/xend/XendClient.py
tools/python/xen/xend/XendDomain.py
tools/python/xen/xend/XendDomainInfo.py
tools/python/xen/xend/server/SrvDomain.py
tools/python/xen/xend/server/SrvUsbif.py
tools/python/xen/xm/main.py
xen/arch/x86/domain.c
xen/common/dom0_ops.c
xen/common/domain.c
xen/include/public/dom0_ops.h
xen/include/public/xen.h
xen/include/xen/sched.h